docs: prune AGENTS.md - #209
Merged
Merged
Conversation
85 lines to 66. Every rule that was live stays live; what goes is boilerplate, lookups the environment already answers, and one bullet that had outgrown its neighbours. The `warn_at_caller` rule went from 12 lines to 5. Its three siblings run 2-3 lines each, and most of its bulk was an inventory of which surviving literal `stacklevel` sits at 3, which at 4, and the frame arithmetic behind each. The rule an agent has to follow is that neither depth is constant and the helper walks out instead; the arithmetic belongs in #202, which measured it, so the bullet now points there. `## Agent skills` spent three `###` subheadings and 13 lines carrying three one-sentence pointers. Now a three-bullet list, 5 lines, same three pointers. Deleted: the "This file provides guidance to Claude Code" opener; `just --list, or read it`, which restates what the justfile answers; "Read them." and the `lite_bootstrap/` prefix in Architecture, where the naming convention is the part worth stating because it says where a new file goes; and two of the three alias examples, since one worked example carries the rule. The type-checking rule ended "Do not add it, and do not act on its diagnostics." Naming the forbidden tool keeps it in view, so it is now stated as the target behaviour: `ty` is the only supported type checker, act on its diagnostics alone, and adding Pyright yields noise rather than findings. Same guardrail, no prohibition to read past.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
85 lines to 66. No rule is dropped and no behaviour changes — what goes is boilerplate, lookups the
environment already answers, and one bullet that had outgrown its neighbours.
The
warn_at_callerbullet: 12 lines to 5#208 grew this rule to 12 lines against siblings of 2-3. Most of the bulk was an inventory: which
surviving literal
stacklevelsits at 3, which at 4, and why one is a frame shallower than theother.
That arithmetic is worth knowing and is not worth carrying on every turn. The rule an agent has to
follow is that neither depth is constant and the helper walks out to the first frame outside
lite_bootstrap; the measurements live in #202, so the bullet points there instead of restatingthem.
## Agent skills: 13 lines to 5Three
###subheadings, each wrapping a single sentence, to carry three pointers. Now athree-bullet list under
## Agent docs. Same three pointers, same targets, none of the scaffolding.Deletions
This file provides guidance to Claude Code (claude.ai/code)...— boilerplate that changes nobehaviour.
just --list, or read it— the justfile answers this, and cannot go stale doing so.Read them.and thelite_bootstrap/prefix in Architecture. The directory is discoverable; thenaming convention is the part worth stating, because it says where a new file goes.
One rewording
The type-checking rule ended
Do not add it, and do not act on its diagnostics.Steering byprohibition keeps the forbidden tool in view, so it is now the positive target:
tyis the onlysupported type checker, act on its diagnostics alone, and adding Pyright yields noise rather than
findings. The guardrail is unchanged; there is just no ban to read past.
Say the word if you would rather keep the explicit prohibition — it is a one-line revert.